<html>
<head><h1>Release</h1>  </head>
<body>
 
<a name="top"><h2>Content: </h2></a>
<h3>1.<a href="#introduction">Introduction</a></h3>
<h3>2.<a href="#document">Document report</a></h3>
<h3>3.<a href="#conclusion">Conclusion</a></h3>
 
Release:
<h3>1.<a name="introduction">Introduction:</a> </h3>
<p>
The project evolved the team grew, although more time was spent determining the scope of each sprint. But the planning team developed and signed a formal proposal to indentify the milestones for each sprint.</p>
<p>
 In the project processes, team would write proposals before each sprint, we would have emphasized the shared goals and responsibilities and avoided some problem including late in completing work that the team needed to complete a sprint. The team would have weekly meeting scrum to review status and discuses major problems that prevented the project from moving forward even to improve coordination between the teams. The code was kept in a working state at all times from week 6, with any exception noted mail, so that every member could see the real progress and deliveries the code between team. </p>
<p>
For the coordination, we still keep some of requirement analysis, research and design the architechure would be closer and meet the requirement. We also deliver working software and document early and often to make the respond quickly and easy change the problem. The team was eager to start work to complete every week job while the other finished for the dead line in the currently week. The team could work on the round cycle such as analysis and testing.  </p>
<p>
In this release, we will indicate some of design document, some of project design and testing information. </p>
<hr>
<h3>2.<a name="document">Project document:</a> </h3>
	
<li>(1)<a href = "A7.html">Requirement & analyze:</a> A7 project for uniLearn requirement & analyze by group </li>
	<li>(2)<a href="imageFile/script01.jpg">Design script1</a>,<a href="imageFile/Script02.jpg"/>  Design script2:,</a> A9 project for design script by Ben</li>
	<li>(3)Prepare the project program and wiki: 
A8 project for how to install the project into Google code web site by snoopy </li>
<li>(4)<a href="treeItem.html">Project Priority item:</a> A9 project for backlog priority item by Winnie</li>
	<li>(5)<a href="imageFile/design1.jpg"> Design:</a> A9 project for Design by Jacky</li>
	<li>(6)<a href="#testing">Software testing:</a> A9 Project for software testing report by Ben </li>
<hr>
 <a name="testing"> Software testing:</a>
Processing layer: 
<h3>Success case (white box)</h3> 
<li>1.	When student want to submit assignment, they need to login unilearn first. </li>
<li>2.	After they login, student can select subject. </li>
<li>3.	In the subject page, it has assignment options, after submit it, student can select specific assignment. </li>
<li>4.	Then it will change to assignment page, student can select the file Image that want to submit (file/image has limited size)</li>
<li>5.	After press “submit” button, a pop up window will occur and ask confirm or not press “Yes”. </li>
<li>6.	Then the submission information will show press ‘print’ button to print the detail. </li>
<li>7.	After it, return to main page. </li>
<br>
<h3>Un-success case (black box) </h3>
<li>1.	If student type in name/password wrong over three times, system will not accept login request in ten minutes. </li>
<li>2.	If file/image size are too big and format are not correct, after ten to fifteen times, it will back to main –page. </li>
 
	
 
<h3>3.<a name="conclusion">Conclusion:</a></h3>
<p>
For evaluating project achieve, studying from team indicates that on time delivery and effective collaborative form important factors that lead to project success.
</p> 
<a href="#top">Content</a>
</body>
</html>
